5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
- Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 3-17: Using Event Points

Pre-User Selection


The Pre-User Selection event point executes after a PCF record is read and before APPX applies the selection criteria. It executes once for every record in the PCF that satisfies the constraints of the Establish PCF Range event point, or whatever APPX constructs in the absence of statements in that event point.

This event point is used to select records that cannot be included or excluded through the normal record selection specifications; their selection may be dependent upon a highly complex combination of selection criteria, for example. Pre-User Selection routines become part of the selection criteria for the query.

The INCLUDE RECORD predefined field determines whether or not a record is selected for the query. INCLUDE RECORD is reset to blank immediately before the Pre-User Selection event point executes. To exclude the record, regardless of the selection criteria, set INCLUDE RECORD to 0 or N (no) in the event point. To include the record, regardless of the selection criteria, set INCLUDE RECORD to 1 or Y (yes) in the event point. If INCLUDE RECORD is left blank, the record is included or excluded based on the selection criteria.

MENU, INPUT, OUTPUT, INQUIRY, JOB, STATUS, UPDATE, and QUERY statements should not be entered in the Pre-User Selection event point. Additionally, display control statements such as DISPLAY, BLINK, NO INPUT, OK INPUT, etc. should not be entered here. APPX will ignore all such statements at runtime.

Be aware that performance can be significantly affected based on the location of event point statements. Remember that statements in Pre-User Selection are executed with every PCF record accessed while those in Post User Selection are only executed after a record has been selected. For example, if statements are required to read auxiliary files and access fields evaluated in the selection of records, place the statements here. However, if the statements access files to get field values used to determine the sort pattern for selected records, place the statements in Post User Selection.

Application Design Manual                                         "Powered by Appx Software"

477

©2006 By APPX Software, Inc. All Rights Reserved